-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subject id search #4881
Subject id search #4881
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4881 +/- ##
=======================================
Coverage 84.77% 84.77%
=======================================
Files 319 319
Lines 19296 19296
=======================================
Hits 16358 16358
Misses 2938 2938 ☔ View full report in Codecov by Sentry. |
Quality Gate passedIssues Measures |
Unfortunately we can't quite index this fully as it is: the name query is for all collaborators, and for all individuals and we can't index on both arrays simultaneously. Fortunately the collection is pretty small and the individuals array is short so this should work out anyway. |
@@ -145,11 +145,18 @@ | |||
"case": [ | |||
IndexModel([("synopsis", TEXT)], default_language="english", name="synopsis_text"), | |||
IndexModel([("causatives", ASCENDING)], name="causatives"), | |||
IndexModel([("suspects", ASCENDING)], name="suspects"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed this one missing in passing.
@@ -167,6 +167,7 @@ def _set_case_name_query(self, query: Dict[str, Any], query_term: str): | |||
query["$or"] = [ | |||
{"display_name": case_name_regex}, | |||
{"individuals.display_name": case_name_regex}, | |||
{"individuals.subject_id": case_name_regex}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only change, really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Did you test it?
* Fix Clinical-Genomics#4878 - search subject id, add supporting indicies * changelog * add a couple of commas * actually spell * query is for collaborators and individuals. cant do dual array indicies yet. --------- Co-authored-by: Chiara Rasi <[email protected]>
* Fix Clinical-Genomics#4878 - search subject id, add supporting indicies * changelog * add a couple of commas * actually spell * query is for collaborators and individuals. cant do dual array indicies yet. --------- Co-authored-by: Chiara Rasi <[email protected]>
This PR adds a functionality or fixes a bug.
Testing on cg-vm1 server (Clinical Genomics Stockholm)
Prepare for testing
scout-stage
and the server iscg-vm1
.ssh <USER.NAME>@cg-vm1.scilifelab.se
sudo -iu hiseq.clinical
ssh localhost
podman ps
systemctl --user stop scout.target
systemctl --user start scout@<this_branch>
systemctl --user status scout.target
scout-stage
) to be used for testing by other users.Testing on hasta server (Clinical Genomics Stockholm)
Prepare for testing
ssh <USER.NAME>@hasta.scilifelab.se
us; paxa -u <user> -s hasta -r scout-stage
. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.conda activate S_scout; pip freeze | grep scout-browser
bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
us; scout --version
paxa
procedure, which will release the allocated resource (scout-stage
) to be used for testing by other users.How to test:
Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.
Review: